ASSETS-35923 create .cloudmanager/java-version for cloud projects, min jdk11 #1175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Projects created for cloud should be expected to build with a minimum jdk version of 11.
Description
.cloudmanager/java-version
for cloud projects with text content11
, per Setting the Maven JDK Versionit-java8
profile that changes thearchetype.test.projectsDirectory
when executed with jdk 1.8 to point to a new sibling folderprojects-1_8
containing symbolic links to non-cloud IT project directories, so that the archetype project itself continues to build successfully for both jdk1.8 and jdk11 executions.Related Issue
ASSETS-35923 Release 15262 aem-sdk-api breaks the sample unit tests in aem-project-archetype projects when running under JDK8, including new sandbox programs
Motivation and Context
Upstream project dependencies of AEM are gradually moving to Java 11+ targets, which are compatible with the AEM Cloud Service runtime, but not compatible with the default Cloud Manager JDK version 1.8. Until the minimum supported version of AEM on AMS/On-Prem is raised above 1.8, the archetype should extend its conditional logic for cloud vs non-cloud to govern the required JDK version as well, so that cloud projects and the cloud SDK can evolve more cohesively.
How Has This Been Tested?
Executed the archetype locally under jdk 1.8 and jdk 11 to confirm that the tests pass and that the aemVersion=cloud IT projects contain a
.cloudmanager/java-version
file with the contents11
and that they fail early if they are built with jdk 1.8.Screenshots (if appropriate):
Types of changes
Checklist: